home *** CD-ROM | disk | FTP | other *** search
- Path: vb.franken.de!volker
- From: volker@vb.franken.de (Volker Barthelmann)
- Subject: Re: PPC compilers
- Newsgroups: comp.sys.amiga.programmer
- References: <4com6v$415@maureen.teleport.com> <jasonb.821098303@cs.uwa.edu.au> <volker.0e58@vb.franken.de> <jasonb.821177376@cs.uwa.edu.au>
- X-Newsreader: TIN [AMIGA 1.3 950726BETA PL0]
- Message-ID: <volker.0e5y@vb.franken.de>
- Date: 10 Jan 96 01:41:04 MET
- Organization: home
-
- Jason S Birch (jasonb@cs.uwa.edu.au) wrote:
- :
- : How about bitfields? They can hide information about what particular
- : bits are used for, and their order in the structure.
-
- Many HLLs do not have something like bitfields. Also C's definition is
- not very precise.
-
- And, most important, You cannot declare every possible hardware registers
- with bitfields (e.g. if one value crosses a word boundary).
-
- : >You sometimes need to know it in HLLs, too. Numerical calculations almost
- : >always need very detailed information on the data types. Just have a look
- : >at a C compiler's float.h.
- :
- : I wouldn't say "almost always" - in any case, by using the #defined
- : labels, you are *still* portable and hiding the implementation details
- : from yourself.
-
- Often it's not possible to write really portable code with floating point
- calculations. Of course almost all common systems seem to use IEEE and
- therefore no problems occur.
-
- : >In many cases You can forget such things after the declaration, but there
- : >are lots of other cases, too.
- :
- : Perhaps, but I'll wager they're extremely rare - with assembler, which
-
- I wouldn't say "extremely rare". :-)
-
- : is what the discussion was about, you constantly need to remind
- : yourself of those implementation details, and consistently get it
- : right.
-
- Yes.
-
- Volker
-
-